Skip to content

Conversation

@garyo
Copy link
Contributor

@garyo garyo commented Nov 14, 2025

There's no need to have our own WINDOWS #define; Windows always predefines _WIN32. Tested with our CMake/Conan build on Mac & Windows. This should clean things up in preparation for publishing a proper Conancenter recipe for OpenFX that doesn't cause users of the recipe to get WINDOWS definitions in their builds.

Copy link

@jfpanisset jfpanisset left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you still need WIN32 and WIN64 symbols in .vcproj project files?

Outside of the .vcproj / .dsp project files, as far as I can tell those are still referenced in:

  • HostSupport/include/ofxBinary.h line 9
  • include/ofxCore.h line 25
  • Examples/DrawSuite/drawsuite.cpp line 15
  • Examples/Overlay/overlay.cpp line 15
  • Examples/Custom/custom.cpp line 11
  • cmake/OpenFX.cmake lines 6, 17
  • Documentation/sources/Guide/Code/NMakefileCommon line 22

Of course it is possible that some of the OpenFX client code ends up depending on these WIN32 / WIN64 symbols, so you may end up having to keep defining them, but it would be preferable (?) if the OpenFX code just used the pre-defined _WIN32 symbol?

@garyo
Copy link
Contributor Author

garyo commented Nov 14, 2025

Do you still need WIN32 and WIN64 symbols in .vcproj project files?

Ah, I should remove those too. Will do.

Copy link

@jfpanisset jfpanisset left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, avoiding custom symbols that look like system defined ones is always good.

@garyo garyo merged commit 3722475 into main Nov 19, 2025
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants